Joomla! Community & Leadership Blogs
Blogs
Joomlacode.org, which hosts the Joomla download files, issue trackers and other Joomla related projects, will be updated this weekend. The underlying GForge code will be updated from an old, out of date version to the current GForge release.
The update will put Joomlacode.org on a much more solid foundation. (Imagine how we would feel if someone was running an old Joomla version like 1.6.2!) There are many new features and bug fixes in the new GForge version. The update will also make it much easier for us to keep up with new GForge releases going forward.
To install the update, Joomlacode.org will be down for about two hours, starting Monday at 02:00 GMT (see this link for your time zone). This means that all projects hosted at Joomlacode.org will be unavailable during this time. This includes download files, auto-update files, issue trackers, code repositories, wikis, and any other Joomlacode.org resource.
After the update, the site will be available with all prior data but with the new GForge software version. A group of volunteers has tested the updated software and no major issues are expected. However, as with any software update, there is always the possibility that something won’t work as expected.
If you find any problem with Joomlacode.org after the update, please report it on the Joomla! Bug Squad list (email to or go to https://groups.google.com/forum/#!forum/joomlabugsquad).
Most of the site functions will be similar and recognizable after the update. There are a few changes specifically to the trackers used by the Bug Squad that we will document on the wiki here: https://docs.joomla.org/Issue_Tracker_Changes.
The Joomla project owes a huge “thank you” to Tony Bibbs and his team at GForge. They have graciously volunteered their time and resources to do this update.
- Details
The numbering of the CMS version 3 releases that are coming in the next day or so is going to be a bit surprising. Maybe not as strange as going from 1.7 to 2.5, but let’s take a closer look so everyone understands what is going on.
As previously posted, the plan was for a release of 3.1.2 early this week. However some people automatically updated prior to the release due to receiving premature notification of the release while final testing of the release packages by the Joomla! Bug Squad was beginning.
When they updated they found that, in fact, there was a problem with the packages. That problem caused their updates to fail, breaking their sites. After several intense days of investigation, it was determined that the failure was due to changes to a key file (restore.php) in the update component itself. This caused the updates to fail before completing.
Once the cause of the problem was identified, a solution was sought. Although it seems as though a limited number of sites were impacted by this change, it is important to provide them with a way to update successfully using the automatic updater, which the corrupted file would prevent.
After a lot of head scratching, experimentation and testing a workable plan was developed. That is where the strange release schedule and numbers come in.
3.1.2, the release that was never released, will not have a formal release.
3.1.3 will be a release that will only replace the corrupted file. Only users who installed 3.1.2 will install 3.1.3. Everyone else will skip 3.1.2 and 3.1.3 and go straight to 3.1.4.
- Users currently on 3.1.1 will go directly to 3.1.4.
- Users who accidentally went to 3.1.2 will go to 3.1.3 and then 3.1.4.
All of this will work seamlessly in the Joomla update component.
Thanks as always to the people who test the pre-release CMS packages and to those who accidentally updated and quickly reported problems. This participation means that no broken version of the CMS was released and is what makes Joomla! not just such a powerful application but also a great development and user community to be a part of.
Though 3.141592 has been suggested as the next release, most likely we’ll have a 3.1.5 in August just before the beta of 3.2.
Update: Added missing paragraph and missing dots in title.
- Details
On Sunday evening, the PLT began its pre-release procedure in preparation of the upcoming 2.5.12 and 3.1.2 releases, originally scheduled for release today.
During this procedure, pre-release packages are posted to Joomlacode and made available to the Joomla Bug Squad for final testing. Typically, these packages are not visible to everyone. However, since there are no security issues included in this release, these pre-release packages were not hidden. This caused third party update services such as Akeeba Admin Tools to erroneously report that these releases were available and as such several hundred sites were updated before the packages were hidden on Monday morning.
- Details
- Written by: The Joomla Project
Joomla! User Groups (JUGs) beat at the heart of the Joomla! project, providing a regular opportunity for members of the community to come together, share their knowledge, learn, and meet others from their local area.
There are Joomla! User Groups around the world, all of which are run by volunteers. A team of volunteers also makes up the Joomla! User Group Team, who are responsible for approving JUG applications, supporting new User Groups during the application process, in the early days when the JUG is getting started and dealing with any issues which may arise in relation to Joomla! User Groups.
- Details
- Written by: Ruth Cheesley
Open Source Matters, Inc. ("Open Source Matters" or "OSM") is planning to extend the options for use of a demo site on https://demo.joomla.org as well as offer a new free hosting option. The contract with the current Joomla demo vendor is expiring soon and OSM has determined that in the interest of fairness and equality, other vendors should also have the opportunity to submit proposals for the following request for proposals.
Open Source Matters is requesting proposals for TWO different options that may be offered to new potential Joomla CMS users.
Interested web hosting companies can find information and detailed requirements for the two requests for proposals can be found here: OSM Request For Proposals Demo Site July 2013
Any updates to the RFP will be listed below with our changelog.
RFP CHANGELOG
Version 1.1 (updated August 13, 2013)
Updated an incorrect 12 month average for the number of demo site signups for the months of July 2012 - June 2013.
- Details